Systems, methods, and devices for securely managing network connections

ABSTRACT

The disclosure relates generally to methods, systems, and apparatuses for managing network connections. A method may include identifying a first state of a first endpoint connection of a first networked machine and a second state of a second endpoint connection of a second network machine, and confirming the first state and the second state based on expected states for the first networked machine and the second network machine, wherein the expected states comprise a list of expected connections.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/079,849, filed Mar. 24, 2016, the entire contents of which is herebyincorporated by reference.

TECHNICAL FIELD

The disclosure relates generally to methods, systems, and apparatusesfor securely managing network connections.

BACKGROUND

Computing devices often communicate across networks, such as a localarea network (LAN), wide area network (WAN), the Internet, and/or thelike. Because computing systems are often used to control importantoperational systems, store or access confidential data, or perform otherimportant or sensitive functions, security of computer systems is ofgreat importance. In some cases, security may be increased by limitingor controlling which devices or systems with which a specific computingsystem is allowed to communicate.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive implementations of the presentdisclosure are described with reference to the following figures,wherein like reference numerals refer to like parts throughout thevarious views unless otherwise specified. Advantages of the presentdisclosure will become better understood with regard to the followingdescription and accompanying drawings where:

FIG. 1 is a schematic block diagram illustrating an example operatingenvironment for a management host, according to one implementation;

FIG. 2 is a schematic block diagram illustrating example components of amanagement host, according to one implementation;

FIG. 3 is a schematic signal diagram illustrating a method for managingcommunication configurations at endpoints, according to oneimplementation;

FIG. 4 is a schematic flow chart diagram illustrating a method formanaging network connections, according to one implementation; and

FIG. 5 is a block diagram depicting an example computing device orsystem consistent with the enabling disclosure of the computer processestaught herein.

DETAILED DESCRIPTION

Current approaches to securing a system focus on securing or configuringendpoints of communications. For example, IP tables, a core tool inLinux™ for securing systems, can allow a specific system to deny accessto the system based on ports and Internet Protocol (IP) address blocks.Amazon Web Services™ (AWS) provides security groups by specifyingallowed connections to and from other security groups, which may includemore than one machine or address.

Applicants have recognized that current technologies do not provide anefficient method of confirming that the allowed connections are completeand correct. Within a software product, there may be internalconnections between dedicated services that require two endpoints on twoor more machines. Because existing technologies are configured on asingle endpoint basis, this approach risks mismatched configurations.For example, one machine may be permissive for a connection while theother is not. Amazon provides a tool, CloudFormation™, for the creationof security groups, but it explicitly requires a single end approach.When two security groups are required to communicate, an administratorneeds to enter two rules in the template, as stated in the followingquote for AWS CloudFormation™ found athttp://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-security-group.html:

-   -   If you want to cross-reference two security groups in the        ingress and egress rules of those security groups, use the        AWS::EC2::SecurityGroupEgress and AWS::EC2::SecurityGroupIngress        resources to define your rules. Do not use the embedded ingress        and egress rules in the AWS::EC2::SecurityGroup. If you do, it        causes a circular dependency, which AWS CloudFormation doesn't        allow.

Based on the foregoing limitations, Applicants have developed systems,methods, and devices that improve network connection management.Applicants recognized that, in at least one embodiment, managing networkcommunication permissions from the perspective of two endpointstogether, rather than managing endpoints separately, leads to greatercontrol and efficiency.

In one embodiment, a system for managing network connections may store alist of expected connections for a plurality of managed machines,devices, or computing systems. For example, the list of expectedconnections may be stored using a mark-up language or data serializationstandard, such as YAML. YAML stands for YAML Ain't Markup Language andaims to be a human readable standard for many or all programminglanguages. In one embodiment, each connection in the list of expectedconnections is defined with a starting point, an end point, an IPprotocol, and a port number or range of port numbers. The managingsystem may also include a tool to examine and create necessarypermissions at both end points, a tool to validate these connections,and/or a tool to specify mappings, if end points map to multiplemachines. One or more of these tools may be used to aggregate connectioninformation on remote machines to a single machine (e.g., the managingsystem) and the ability to push configurations from the single machineto remote machines.

In one embodiment, a list of expected connections, such as the YAML filedescribing connections, may be managed as a source code artifact (usingany number of source code versioning systems). The most recent versionmay then be used to validate existing configurations or connectionsagainst that defined in the list. In one embodiment, changes made inlive configurations can be checked against expected configurations, andalerts generated if the configurations are out of sync.

In one embodiment, a system for managing network connections includes astorage component, a decoding component, a rule manager component, and anotification component. The storage component is configured to store alist of expected connections for a plurality of networked machines. Eachconnection in the list of expected connections defines a start point andan end point for the connection. The decoding component is configured todecode messages from the plurality of networked machines indicating oneor more connections for a corresponding machine. The rule managercomponent is configured to identify an unexpected presence or absence ofa connection on at least one of the plurality of networked machinesbased on the list of expected connections. The notification component isconfigured to provide a notification or indication of the unexpectedpresence or absence.

Referring now to the figures, FIG. 1 illustrates an example system 100that provides an operating environment for a management host 102. Thesystem 100 includes a plurality of managed computing systems 104 and aplurality of external systems 106. The management host 102 and computingsystems 104 may include computing devices such as servers, virtualmachines, or any other computing device that make up part of a networkedcomputing system 108. The management host 102 and computing systems 104of the network computing system 108 may be physically located within thesame data center or server farm, or may be located remotely from eachother and may be commonly managed by the management host 102. Theexternal systems 106 represent systems that are not managed by themanagement host 102, and may include computing systems that are locatedwithin the same data center or remote from the management host 102. Eachof the management host 102, computing systems 104, and external systems106 may be connected to one or more networks or networking devices,which allow them to communicate with each other. For example, themanagement host 102, computing systems 104, and external systems 106 maycommunicate with each other over the Internet, through private networks,or any type of network.

Each of the internal or managed computing systems 104 may storeconnection configurations, such as in a configuration file, for itself.The connection configurations may be stored in a routing table, IPtable, firewall, or any other format or program. The connectionconfigurations may indicate other devices, addresses, or security groupsthat are allowed to communicate with the computing system 104. Theconnection configurations may specify a communication direction (e.g.,inbound or outbound), address, port number (or range of port numbers),security group identifier, or the like for a specific connection. Asecurity group identifier may include a name, number or other identifierthat corresponds to a plurality of machines or addresses. For example, afirst security group 110 includes two managed computing systems 104, anda second security group 112 includes two external systems 106. Thus, aconnection entry in a configuration file for a specific computing system104 may indicate that a computing system is allowed to communicate(either in-bound or out-bound) with any system in the first securitygroup 110 or the second security group 112 without explicitlyidentifying machines in the security groups. In one embodiment, eachcomputing system 104 only stores configurations for itself.

The management host 102 stores a connections master file, which includesmaster information for all the managed computing systems 104. Forexample, the connections master file may include a list of expectedconnections for all of the managed computing systems 104 in thenetworked computing system 108. Thus, in one embodiment, the list storesconnection information for each of the computing systems 104, such thatall of the configurations for the computing systems 104 are stored inthe connections master file. The connections master file may be storedbased on any file format, such as a markup language or a dataserialization standard. According to one embodiment, the connectionsmaster file comprises a YAML file.

With the connections master file stored by the management host 102, themanagement host may then monitor actual configurations for the computingsystems 104 (e.g., based on the configuration files). In one embodiment,each of the computing systems 104 may periodically, or in response to arequest, send its configuration file to the management host 102. Whenthe configuration files have been received by the management host 102,the management host 102 may compare the configuration files to theconnections master file to detect any differences. In one embodiment,the differences may include the presence of an unexpected connection ina configuration file at a computing system. For example, a connectionentry in a configuration file may not have a corresponding entry in theconnections master file. In one embodiment, the differences may includethe absence of an expected connection in a configuration file at thecomputing system. For example, a connection entry in the connectionsmaster file may not have a corresponding entry in the configurationfile(s) for the correct one or more computing systems 104.

The differences identified by the management host 102 may indicate thatthere is an error/omission with either the connections master file orthe configuration file(s) for one or more computing systems 104. Forexample, if there is an unexpected connection in a configuration file(with respect to the connections master file) it may be that theconnections master file has been incorrectly configured and theunexpected connection actually should be in the connections master file.On the other hand, the unexpected connection may reflect that theconfiguration file for the computing system 104 is incorrect and thatthere is a security risk or operational risk for the computing system.

In one embodiment, the management host 102 and its functions andfeatures may provide significant benefits over other availabletechnologies. For example, existing technologies that are all singleend-point based do not have an easy mechanism to monitor existingconfigurations against expected configurations. Because the managementhost 102 provides an easy and quick way to monitor and manageconnections on a connection basis, rather than on a single end-pointbasis, the management host 102 increases security and reduces costs inmonitoring. Furthermore, these monitoring aspects can act as validcontrols for various security certifications, including the ServiceOrganization Control 2 (SOC2) certification and Health InsuranceAccountability Act (HIPAA) certification and compliance, for example.

In one embodiment, the management host 102 and connections master filemay be used to manage security group configurations in existing cloudservices, such as in Amazon's AWS™ accounts. In one example, AWSsecurity groups may be used at endpoints, along with external subnets asrequired. The connections master file (such as a YAML file) may notethat a certain service or machine needs to communicate with anotherservice or machine. Running a rule manager, the management host 102 canensure that the rule exists at the endpoints. The rule manager may alsoexamine rules in a security group, and delete those rules that are notexpected. In one embodiment, the rule manager may operate as a validator(for example, in response to flags when initiating the rule manager) toprovide a count of differences between the expected set of rules (e.g.,in the connections master file) and the existing rules (e.g., in theconfiguration files).

For illustration purposes, an example rule might be one that allowsexternal load balancers to talk on a single port to Global Services (GS)instances. An administrator may define a security group prod_elb for theelastic load balancers, and prod_gs for global services, which identifythe machines, addresses, identifiers, or the like that belong to eachgroup or service. The rule may be stored in a YAML file as follows:

-   -   source: prod_elb    -   destination: prod_gs    -   protocol: tcp    -   service: snowflake_elb

The above rule tells a rule manager (e.g., the management host 102 or aservice run on the management host 102) to expect a port, defined assnowflake_elb (e.g., with a value 8084) to be opened with thetransmission control protocol (TCP) with an outbound rule on prod_elb toprod_gs, and an inbound rule on prod_gs from prod_elb. A second mappingfile may be used to define which machines (e.g., addresses, identifiers,etc.) have the role for Global Services (GS) to include prod_gs as asecurity group, and load balancers to include prod_elb. Example code forGS may be as follows:

role: GS

groups:

-   -   group: prod_gs    -   group: prod_core

In one embodiment, the role for GS is included with a prod_gs group anda second group, prod_core, for rules shared across all instances. Forexample, a role may belong to more than one security group (Amazon AWS™allows up to five security groups on each instance). In one embodiment,the management host may execute a validation program to confirm all GSinstances are running with both security groups.

The above example is illustrative only and includes teaching andprinciples that may be expanded to apply to any multi-endpointconfiguration. In one embodiment, the management host 102 may then push(or the managed computing systems 104 may pull) configurations to theend-points. In one embodiment, the actual configuration at an end-point(e.g., a managed computing system 102) may be requested by and/or sentto the management host 102. Furthermore, a wide variety of file formattypes or communication configurations for end-points are contemplatedwithin the scope of the present disclosure. For example, end-points mayeach have route tables and may be managed by a single route tablemanager on a management host 102.

FIG. 2 is schematic a block diagram illustrating example components of amanagement host 102. In the depicted embodiment, the management host 102includes a storage component 202, a decoding component 204, a rulemanager component 206, a notification component 208, and a pushcomponent 210. The components 202-210 are given by way of illustrationonly and may not all be included in all embodiments. In fact, someembodiments may include only one or any combination of two or more ofthe components 202-210, without limitation. Some of the components202-210 may be located outside the management host 102 on differentsystems or machines or the management host 102 may include a pluralityof different machines or systems that include one or more of thecomponents 202-212.

The storage component 202 is configured to store a list of expectedconnections for a plurality of networked machines, such as the managedcomputing system 104 of FIG. 1. In one embodiment, each connection inthe list of expected connections defines a start point and an end pointfor the connection. The list of expected connections may be stored aspart of a YAML file, or any other format or type of file. The list ofexpected connections may include keywords that define actions for theconnection, such as whether a connection is external or internal only(whether it allows non-managed devices or systems to connect using thatconnection). In one embodiment, the list of expected connections may bestored in source control to provide version tracking for the list.

Each entry in the list may include a plurality of additionalrequirements for the connection, such as a protocol, a port number, anda port number range for the corresponding connection or communication.In one embodiment, the starting point and/or the end point for aconnection in the list of expected connections includes a group, such asa security group. Use of groups may allow any member of that group totake part in the communication (according to the communication orconnection requirements) without the member being specificallyidentified.

The storage component 202 may store the list of expected connections ina connections master file local to the management host 102 or may storethe list on a network accessible storage location.

The decoding component 204 is configured to receive and/or decodemessage from one or more machines managed by the management host 102.For example, the decoding component 204 may include a network interfacecard (NIC), routing component, or other hardware or software to receive,decode, parse, or otherwise process messages from managed devices. Themessages may include information indicating one or more connections fora corresponding machine. For example, the messages may include one ormore of a current connection or a configured connection for thecorresponding machine. For example, the messages may include informationin a configuration file or may include information reflecting actualcurrent communication connections of a specific machine at a specifictime. In one embodiment, the messages may include a route table for amachine, configurations for a firewall, or other information about whatconnections are allowed or not allowed by a specific machine or system.

The rule manager component 206 is configured to determine whetherconnections or configurations at end-points, such as computing systems104, comply with the list of expected connections. In one embodiment, arule manager component 206 is configured to identify an unexpectedpresence or absence of a connection on at least one of the plurality ofnetworked machines based on the list of expected connections. In oneembodiment, the rule manager component 206 is configured to determinethat a connection of the one or more connections for the correspondingmachine is expected when there is a matching entry in the list ofexpected connections. In one embodiment, the rule manager component 206is configured to identify the presence of the unexpected connectionbased on a connection having no matching entry in the list of expectedconnections. In one embodiment, the rule manager component 206 isconfigured to identify the unexpected absence of a connection based onan entry in the list of expected connections having no matchingconnection in the one or more connections for the corresponding machine.

In one embodiment, the rule manager component 206 is configured tovalidate the completeness and/or accuracy of communicationconfigurations. For example, the rule manager component 206 may count anumber of differences between the list of expected connections and theactual configurations of managed systems. If the number of differencesis non-zero, this may mean that either the list of expected connectionsis inaccurate or that the end-points are incorrectly configured. In oneembodiment, an administrator may be notified if there are differencesand the administrator will determine whether a change needs to be madeto the list of unexpected connections. The validation role performed bythe rule manager component 206 may allow for a determination of whetherthe configuration matches the expected configuration and makes it easyfor administrators to identify where any differences are. For example,it may be easily determined that all endpoints are configured inaccordance with the list of expected connections within a connectionsmaster file.

In one embodiment, the rule manager component 206 is configured toenforce the expected connections in the list of expected connections.For example, the rule manager component 206 may push configurations downto each end-point based on the list of expected connections. The rulemanager component 206 may translate an entry in the list into specificrules for each managed end node. For example, the rule manager component206 may convert a rule in a YAML file into a format of a configurationfile. Furthermore, the rule in the YAML file may be converted from awhole connection rule (or both ends of a communication) into a singleend-point rule, for storage by a specific end-point machine. Theseconfigurations that have been pushed or sent down to the endpoints(e.g., using the push component 210) may result in deletion or additionof rules on the endpoint or may result in a replacement of allconnection rules at the endpoint.

In one embodiment, the rule manager component 206 may generally operateas a validator and then, in response to input from an administrator,enforce the expected connections on the endpoints. For example, the rulemanager component 206 may, periodically or in response to a command,perform validation of the configurations at endpoints. If there aredifferences, the rule manager component 206 may cause a message to besent to the administrator (e.g., using the notification component 208).The administrator may then review the differences to determine if anychange needs to be made to the list of expected connections. If nochanges are needed the administrator may then cause the rule managercomponent 206 to push or enforce the changes onto any endpoints that areconfigured differently than required by the list of expectedconnections. If changes are needed, the administrator may then makechange to the list of expected connections and the initiate anothervalidation procedure and/or enforcement of the revised list.

The notification component 208 is configured to provide a notificationto an administrator, managing system, or notification system. In oneembodiment, the notification component 208 may provide a notificationthat includes an indication of the presence or absence of an unexpectedconnection. For example, the notification may identify a connection inthe list of expected connections that is missing from a configuration ofa specific system. As another example, the notification may identify aconnection in a configuration of a specific system that is not in thelist of expected connections stored by the management host. In oneembodiment, the notification may include an indicator for the number ofdifferences between the list of expected connections and actualconnections or configurations on the plurality of machines.

In one embodiment, the notification may be provided to one or more of alog file, a notification area of a user interface, an email address, atext message, or as part of another message. As one example, thenotification component 208 may provide a notification to a monitoringsystem. Nagios™ is one example of a monitoring system that may be usedto deliver notifications. The notification may be sent to anadministrator so that the administrator is apprised of the differenceand can take steps to review and/or correct the discrepancy. In oneembodiment, the notification component 208 is configured to flag anentry in the list of expected connections or in a configuration file ofan endpoint to reflect the unexpected presence or absence of theconnection.

The push component 210 is configured to provide connection rules toendpoints based on the list of expected connections stored by thestorage component 202. For example, an administrator may be able to setup and/or review the list of expected connections and then cause rulesto be created for each endpoint based on the list of expectedconnections. In one embodiment, the push component 210 is configured toadd or delete connection configurations on the plurality of machinesbased on the list of expected connections. For example, the pushcomponent 210 may add a rule to an endpoint that is missing a rulecorresponding to an entry in the list of expected connections. Asanother example, the push component 210 may delete a rule on an endpointthat, based on the list of expected connections, should not be there.

FIG. 3 is a schematic signal diagram illustrating a method 300 formanaging network connections. The method 300 may be performed by amanagement host 102 and one or more managed computing systems 104.

The management host 102 stores at 302 a master connections list in aYAML file. For example, the master connections list may include a listof expected connections and/or a master connections file as discussedherein. The management host 102 may store the YAML file in a versiontracking and control system that tracks changes to the file and can beeffectively monitored and tracked. The management host 102 requests at304 a report of current connections from the managed computing systems104. For example, the management host 102 may periodically send requestsfor current connections to monitor how managed endpoints are configured.In one embodiment, the request may include a request for connectionconfigurations and/or actual current connections of an endpoint.

The management host 102 receives at 306 one or more messages indicatingcurrent connections at the computing systems 104. For example, managedcomputing systems 104 may send messages indicating current connectionconfigurations or current communication connections. The message mayindicate the current connections according to one or more differentformats, such as in an iptable format, AWS™ format, or any other format.Although method 300 illustrates that the messages are received at 306 inresponse to a request from the management host 102, the computingsystems 104 (or other endpoints) may periodically provide informationabout current connections autonomously or without requiring themanagement host 102 to send a request.

In response to receiving the messages at 306, the management host 102detects at 308 differences between the YAML file and the currentconfigurations or connections of the computing systems 104. For example,the management host 102 may check whether each entry in the YAML filehas a corresponding entry in corresponding endpoints and check whethereach entry in an endpoint configuration has a corresponding entry in theYAML file. The management host 102 may count the number of detecteddifferences and/or flag each of the differences. The management host 102may send at 310 a notification that indicates the differences (e.g., thenumber of difference and/or the flagged entries in the YAML file or inendpoint configurations). The notification may be sent at 310 to aninterface or administrator device 314 where an administrator orautomated service can determine how to handle the differences. Forexample, the administrator may be able to review each difference one byone and choose whether to except the YAML file version, the endpointconfiguration version, and/or define a new rule for the YAML file orendpoint. For example, the administrator may recognize that the endpointis configured properly, but the YAML file is missing or incorrect. Onthe other hand, the administrator may confirm that the YAML file iscorrect and the endpoint is incorrectly or improperly configured. Oncethe administrator has determine how to handle the differences, theadministrator may indicate that the YAML file is final (or that aspecific difference is accepted or declined). The interface oradministrator device 314 provides at 312 the accepted or declineddifferences to the management host 102. For example, the accepted ordeclined differences sent by the interface or administrator device 314may include input from the administrator that indicates how to handlethe differences (e.g., delete a rule from a computing system 104 or adda rule to the list in the YAML file).

The management host 102 updates at 316 the connections list in the YAMLfile based on the accepted or declined differences received at 312, asneeded. The box corresponding to updating 316 the connections list isshown with a dotted border to indicate that changes to the connectionslist in the YAML file may not be required based on the input receivedfrom the administrator. For example, the master connections list mayonly be updated if the accepted or declined differences received at 312indicate that a rule needs to be added or deleted from the YAML file.The management host 102 pushes at 318 master configurations to theendpoints, as needed. For example the changes accepted or declined by anadministrator may not require changes to the endpoint configurations ormay require changes to any combination of one or more of the endpoints.

Referring now to FIG. 4, a schematic flow chart diagram of a method 400for managing communication configurations is illustrated. The method 400may be performed by a management host, such as the management host 102of FIG. 1, 2, or 3.

The method 400 begins and a decoding component 204 receives messagesfrom the plurality of networked machines indicating one or moreconnections for a corresponding machine at 402. A rule manager component206 identifies at 404 an unexpected presence or absence of a connectionon at least one of the plurality of networked machines based on the listof expected connections. For example, a connections master list may becompared with the current configurations of the endpoints to determineif there are unexpected connection rules or of there are rules missingfrom the current configurations.

A notification component 208 provides at 406 a notification orindication of the unexpected presence or absence of connections rules.The notification may be sent to a machine or interface for review by anadministrator. The administrator may then take steps to correct eitherconfigurations on an endpoint or within a connections master list orlist of expected connections.

FIG. 5 is a block diagram depicting an example computing device 500. Insome embodiments, computing device 500 is used to implement one or moreof the systems and components discussed herein. For example, computingdevice 500 may allow a user or administrator to access the managementhost 102; or the management host 102, computing systems 104, and/orexternal computing systems 106 may be implemented as a computing device500 with components or modules stored as computer readable code incomputer readable storage media. Further, computing device 500 mayinteract with any of the systems and components described herein.Accordingly, computing device 500 may be used to perform variousprocedures and tasks, such as those discussed herein. Computing device500 can function as a server, a client or any other computing entity.Computing device 500 can be any of a wide variety of computing devices,such as a desktop computer, a notebook computer, a server computer, ahandheld computer, a tablet, and the like.

Computing device 500 includes one or more processor(s) 502, one or morememory device(s) 504, one or more interface(s) 506, one or more massstorage device(s) 508, and one or more Input/Output (I/O) device(s) 510,all of which are coupled to a bus 512. Processor(s) 502 include one ormore processors or controllers that execute instructions stored inmemory device(s) 504 and/or mass storage device(s) 508. Processor(s) 502may also include various types of computer-readable media, such as cachememory.

Memory device(s) 504 include various computer-readable media, such asvolatile memory (e.g., random access memory (RAM)) and/or nonvolatilememory (e.g., read-only memory (ROM)). Memory device(s) 504 may alsoinclude rewritable ROM, such as Flash memory.

Mass storage device(s) 508 include various computer readable media, suchas magnetic tapes, magnetic disks, optical disks, solid state memory(e.g., Flash memory), and so forth. Various drives may also be includedin mass storage device(s) 508 to enable reading from and/or writing tothe various computer readable media. Mass storage device(s) 508 includeremovable media and/or non-removable media.

I/O device(s) 510 include various devices that allow data and/or otherinformation to be input to or retrieved from computing device 500.Example I/O device(s) 510 include cursor control devices, keyboards,keypads, microphones, monitors or other display devices, speakers,printers, network interface cards, modems, lenses, or other imagecapture devices, and the like.

Interface(s) 506 include various interfaces that allow computing device500 to interact with other systems, devices, or computing environments.Example interface(s) 506 include any number of different networkinterfaces, such as interfaces to local area networks (LANs), wide areanetworks (WANs), wireless networks, and the Internet.

Bus 512 allows processor(s) 502, memory device(s) 504, interface(s) 506,mass storage device(s) 508, and I/O device(s) 510 to communicate withone another, as well as other devices or components coupled to bus 512.Bus 512 represents one or more of several types of bus structures, suchas a system bus, PCI bus, IEEE 1394 bus, USB bus, and so forth.

For purposes of illustration, programs and other executable programcomponents are shown herein as discrete blocks, although it isunderstood that such programs and components may reside at various timesin different storage components of computing device 500, and areexecuted by processor(s) 502. Alternatively, the systems and proceduresdescribed herein can be implemented in hardware, or a combination ofhardware, software, and/or firmware. For example, one or moreapplication specific integrated circuits (ASICs) can be programmed tocarry out one or more of the systems and procedures described herein. Asused herein, the terms “module” or “component” are intended to conveythe implementation apparatus for accomplishing a process, such as byhardware, or a combination of hardware, software, and/or firmware, forthe purposes of performing all or parts of operations disclosed herein.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 is a system for managing network connections that includes astorage component, a decoding component, a rule manager, and anotification component. The storage component is configured to store alist of expected connections for a plurality of networked machines,wherein each connection in the list of expected connections defines astart point and an end point for the connection. The decoding componentis configured to decode messages from the plurality of networkedmachines indicating one or more connections for a corresponding machine.The rule manager component is configured to identify an unexpectedpresence or absence of a connection on at least one of the plurality ofnetworked machines based on the list of expected connections. Thenotification component is configured to provide a notification orindication of the unexpected presence or absence.

In Example 2, the list of expected connections in Example 1 includes alist stored in a YAML file format.

In Example 3, the storage component in any of Examples 1-2 is configuredto provide version tracking and control of the list of expectedconnections.

In Example 4, a connection in the list of expected connections in any ofExamples 1-3 further includes one or more of a protocol, a port number,and a port number range for the corresponding connection.

In Example 5, one or more of the starting point and the end point for aconnection in the list of expected connections in any of Examples 1-4includes a group, such as a security group.

In Example 6, the messages in any of Examples 1-5 include one or more ofa current connection or a configured connection for the correspondingmachine.

In Example 7, at least one message of the messages in any of Examples1-6 includes a route table for a machine, wherein the list of expectedconnections includes a master route table.

In Example 8, the rule manager component in any of Examples 1-7 isconfigured to determine that a connection of the one or more connectionsfor the corresponding machine is expected when there is a matching entryin the list of expected connections.

In Example 9, the rule manager component in any of Examples 1-8 isconfigured to identify the unexpected presence of the connection basedon a connection of the one or more connections for the correspondingmachine having no matching entry in the list of expected connections.

In Example 10, the rule manager component in any of Examples 1-9 isconfigured to identify the unexpected absence of the connection based onan entry in the list of expected connections having no matchingconnection in the one or more connections for the corresponding machine.

In Example 11, the notification component in any of Examples 1-10 isconfigured to provide a warning to a log file or a notification area ofa user interface.

In Example 12, the notification component in any of Examples 1-11 isconfigured to provide the notification in a message to an administrator.

In Example 13, the notification component in any of Examples 1-12 isconfigured to flag an entry in the list of expected connections toreflect the unexpected presence or absence of the connection.

In Example 14, the notification component in any of Examples 1-13 isconfigured to determine a number of differences between the list ofexpected connections and actual connections or configurations on theplurality of machines.

In Example 15, the system in any of Examples 1-14 further includes apush component configured to add or delete connection configurations onthe plurality of machines based on the list of expected connections.

Example 16 is a method for managing network connections. The methodincludes storing a list of expected connections for a plurality ofnetworked machines, wherein each connection in the list of expectedconnections defines a start point and an end point for the connection.The method includes receiving an indication from the plurality ofnetworked machines indicating one or more connections for a respectivemachine. The method includes identifying an unexpected presence orabsence of a connection on at least one of the plurality of networkedmachines based on the list of expected connections. The method furtherincludes providing a notification or indication of the unexpectedpresence or absence.

In Example 17, the list of expected connections in Example 16 includes alist stored in a YAML file format.

In Example 18, the method in any of Examples 16-17 further includesproviding version tracking and control of the list of expectedconnections.

In Example 19, a connection in the list of expected connections in anyof Examples 16-18 further includes one or more of a protocol, a portnumber, and a port number range for the corresponding connection.

In Example 20, one or more of the starting point and the end point for aconnection in the list of expected connections in any of Examples 16-19includes a group, such as a security group.

In Example 21, the messages in any of Examples 16-20 include one or moreof a current connection or a configured connection for the correspondingmachine.

In Example 22, at least one message of the messages in any of Examples16-21 includes a route table for a machine, wherein the list of expectedconnections includes a master route table.

In Example 23, determining that a connection of the one or moreconnections for the corresponding machine is expected in any of Examples16-22 includes determining that there is a matching entry in the list ofexpected connections.

In Example 24, determining that a connection of the one or moreconnections for the corresponding machine is unexpectedly present in anyof Examples 16-23 includes determining that a connection of the one ormore connections for the corresponding machine includes no matchingentry in the list of expected connections.

In Example 25, determining that a connection of the one or moreconnections for the corresponding machine is unexpectedly absent in anyof Examples 16-24 includes determining that an entry in the list ofexpected connections includes no matching connection in the one or moreconnections for the corresponding machine.

In Example 26, providing the notification in any of Examples 16-25includes providing a warning to a log file or a notification area of auser interface.

In Example 27, providing the notification in any of Examples 16-26includes providing the notification in a message to an administrator.

In Example 28, providing the notification in any of Examples 16-27includes flagging an entry in the list of expected connections toreflect the unexpected presence or absence of the connection.

In Example 29, the method in any of Examples 16-28 further includesdetermining a number of differences between the list of expectedconnections and actual connections or configurations on the plurality ofmachines.

In Example 30, the method in any of Examples 16-29 further includesadding or deleting connection configurations on the plurality ofmachines based on the list of expected connections.

Example 31 is a system or device that includes one or a plurality ofmeans for implementing a method or realizing a system or apparatus as inany of Examples 1-30.

In the above disclosure, reference has been made to the accompanyingdrawings, which form a part hereof, and in which is shown by way ofillustration specific implementations in which the disclosure may bepracticed. It is understood that other implementations may be utilizedand structural changes may be made without departing from the scope ofthe present disclosure. References in the specification to “oneembodiment,” “an embodiment,” “an example embodiment,” etc., indicatethat the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure, or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to affect such feature,structure, or characteristic in connection with other embodimentswhether or not explicitly described.

Implementations of the systems, devices, and methods disclosed hereinmay comprise or utilize a special purpose or general-purpose computerincluding computer hardware, such as, for example, one or moreprocessors and system memory, as discussed herein. Implementationswithin the scope of the present disclosure may also include physical andother computer-readable media for carrying or storingcomputer-executable instructions and/or data structures. Suchcomputer-readable media can be any available media that can be accessedby a general purpose or special purpose computer system.Computer-readable media that store computer-executable instructions arecomputer storage media (devices). Computer-readable media that carrycomputer-executable instructions are transmission media. Thus, by way ofexample, and not limitation, implementations of the disclosure cancomprise at least two distinctly different kinds of computer-readablemedia: computer storage media (devices) and transmission media.

Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM,solid state drives (“SSDs”) (e.g., based on RAM), Flash memory,phase-change memory (“PCM”), other types of memory, other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to store desired program code means inthe form of computer-executable instructions or data structures andwhich can be accessed by a general purpose or special purpose computer.

An implementation of the devices, systems, and methods disclosed hereinmay communicate over a computer network. A “network” is defined as oneor more data links that enable the transport of electronic data betweencomputer systems and/or modules and/or other electronic devices. Wheninformation is transferred or provided over a network or anothercommunications connection (either hardwired, wireless, or a combinationof hardwired or wireless) to a computer, the computer properly views theconnection as a transmission medium. Transmissions media can include anetwork and/or data links, which can be used to carry desired programcode means in the form of computer-executable instructions or datastructures and which can be accessed by a general purpose or specialpurpose computer. Combinations of the above should also be includedwithin the scope of computer-readable media.

Computer-executable instructions comprise, for example, instructions anddata which, when executed at a processor, cause a general purposecomputer, special purpose computer, or special purpose processing deviceto perform a certain function or group of functions. The computerexecutable instructions may be, for example, binaries, intermediateformat instructions such as assembly language, or even source code.Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the described features or acts described above.Rather, the described features and acts are disclosed as example formsof implementing the claims.

Those skilled in the art will appreciate that the disclosure may bepracticed in network computing environments with many types of computersystem configurations, including, personal computers, desktop computers,laptop computers, message processors, hand-held devices, multi-processorsystems, microprocessor-based or programmable consumer electronics,network PCs, minicomputers, mainframe computers, mobile telephones,PDAs, tablets, pagers, routers, switches, various storage devices, andthe like. The disclosure may also be practiced in distributed systemenvironments where local and remote computer systems, which are linked(either by hardwired data links, wireless data links, or by acombination of hardwired and wireless data links) through a network,both perform tasks. In a distributed system environment, program modulesmay be located in both local and remote memory storage devices.

Further, where appropriate, functions described herein can be performedin one or more of: hardware, software, firmware, digital components, oranalog components. For example, one or more application specificintegrated circuits (ASICs) can be programmed to carry out one or moreof the systems and procedures described herein. Certain terms are usedthroughout the description and claims to refer to particular systemcomponents. As one skilled in the art will appreciate, components may bereferred to by different names. This document does not intend todistinguish between components that differ in name, but not function.

It should be noted that the embodiments discussed above may comprisecomputer hardware, software, firmware, or any combination thereof toperform at least a portion of their functions. For example, a module mayinclude computer code configured to be executed in one or moreprocessors, and may include hardware logic/electrical circuitrycontrolled by the computer code. These example devices are providedherein purposes of illustration, and are not intended to be limiting.Embodiments of the present disclosure may be implemented in furthertypes of devices, as would be known to persons skilled in the relevantart(s).

At least some embodiments of the disclosure have been directed tocomputer program products comprising such logic (e.g., in the form ofsoftware) stored on any computer useable medium. Such software, whenexecuted in one or more data processing devices, causes a device tooperate as described herein.

While various embodiments of the present disclosure have been describedabove, it should be understood that they have been presented by way ofexample only, and not limitation. It will be apparent to persons skilledin the relevant art that various changes in form and detail can be madetherein without departing from the spirit and scope of the disclosure.Thus, the breadth and scope of the present disclosure should not belimited by any of the above-described exemplary embodiments, but shouldbe defined only in accordance with the following claims and theirequivalents. The foregoing description has been presented for thepurposes of illustration and description. It is not intended to beexhaustive or to limit the disclosure to the precise form disclosed.Many modifications and variations are possible in light of the aboveteaching. Further, it should be noted that any or all of theaforementioned alternate implementations may be used in any combinationdesired to form additional hybrid implementations of the disclosure.Further, although specific implementations of the disclosure have beendescribed and illustrated, the disclosure is not to be limited to thespecific forms or arrangements of parts so described and illustrated.The scope of the disclosure is to be defined by the claims appendedhereto, any future claims submitted here and in different applications,and their equivalents.

What is claimed is:
 1. A method of managing a plurality of networkconnections, the method comprising: identifying, by one or more hardwareprocessors, a first state of a first endpoint connection of a firstnetworked machine and a second state of a second endpoint connection ofa second network machine; and confirming the first state and the secondstate based on expected states for the first networked machine and thesecond network machine, wherein the expected states comprise a list ofexpected connections.
 2. The method of claim 1, wherein the list ofexpected connections is stored in a file.
 3. The method of claim 2,wherein the list is stored in human readable data-serialization languageformat.
 4. The method of claim 1, where the expected states compriseeither a presence or an absence of a connection.
 5. The method of claim4, wherein the expected states further comprises one or more of aprotocol, a port number, or a port number range for the first endpointconnection or the second endpoint connection.
 6. The method of claim 1,further comprising providing a notification of the confirming of thefirst state and the second state.
 7. The method of claim 6, whereinproviding the notification comprises providing a message to anadministrator account.
 8. The method of claim 2, wherein the list ismanaged as a source code artifact.
 9. The method of claim 1, whereinconfirming the first state comprising determining that the firstendpoint connection is a permitted connection.
 10. The method of claim1, wherein confirming the first state comprising determining that thefirst endpoint connection is an unpermitted absent connection.
 11. Asystem for managing a plurality of network connections, the systemcomprising: one or more hardware processors to: identify a first stateof a first endpoint connection of a first networked machine and a secondstate of a second endpoint connection of a second network machine; andconfirm the first state and the second state based on expected statesfor the first networked machine and the second network machine, whereinthe expected states comprise a list of expected connections.
 12. Thesystem of claim 11, wherein the list of expected connections is storedin a file.
 13. The system of claim 12, wherein the list is stored inhuman readable data-serialization language format.
 14. The system ofclaim 11, where the expected states comprise either a presence or anabsence of a connection.
 15. The system of claim 11, wherein theexpected states further comprises one or more of a protocol, a portnumber, or a port number range for the first endpoint connection or thesecond endpoint connection.
 16. The system of claim 11, wherein the oneor more hardware processors further to provide a notification of theconfirming of the first state and the second state.
 17. The system ofclaim 16, wherein to provide the notification, the one or more hardwareprocessors to provide a message to an administrator account.
 18. Thesystem of claim 12, wherein the list is managed as a source codeartifact.
 19. The system of claim 11, wherein confirming the first statecomprising determining that the first endpoint connection is a permittedconnection.
 20. The system of claim 11, wherein confirming the firststate comprising determining that the first endpoint connection is anunpermitted absent connection.
 21. A non-transitory computer readablestorage media storing instructions that, when executed by one or morehardware processors, cause the one or more hardware processors to:identify a first state of a first endpoint connection of a firstnetworked machine and a second state of a second endpoint connection ofa second network machine; and confirm, by the one or more hardwareprocessors, the first state and the second state based on expectedstates for the first networked machine and the second network machine,wherein the expected states comprise a list of expected connections. 22.The non-transitory computer readable storage media of claim 21, whereinthe list of expected connections is stored in a file.
 23. Thenon-transitory computer readable storage media of claim 22, wherein thelist is stored in human readable data-serialization language format. 24.The non-transitory computer readable storage media of claim 21, wherethe expected states comprise either a presence or an absence of aconnection.
 25. The non-transitory computer readable storage media ofclaim 24, wherein the expected states further comprises one or more of aprotocol, a port number, or a port number range for the first endpointconnection or the second endpoint connection.
 26. The non-transitorycomputer readable storage media of claim 21, wherein the one or morehardware processors further to provide a notification of the confirmingof the first state and the second state.
 27. The non transitory computerreadable storage media of claim 26, wherein to provide the notification,the one or more hardware processors to provide a message to anadministrator account.
 28. The non-transitory computer readable storagemedia of claim 22, wherein the list is managed as a source codeartifact.
 29. The non-transitory computer readable storage media ofclaim 21, wherein confirming the first state comprising determining thatthe first endpoint connection is a permitted connection.
 30. Thenon-transitory computer readable storage media of claim 21, whereinconfirming the first state comprising determining that the firstendpoint connection is an unpermitted absent connection.